The Events tab logs the user-initiated events as received by the XECUTE server. The grid layout and filter settings are saved in the user's XECUTE cache folder for each site.
The Events grid data can be sorted and filtered like other grids within XECUTE Client.
The events data persists per user session. Reopening XECUTE Client will clear the events list.
| Field Name | Description |
|---|---|
| Received Date (local) | The date and time the update was received by the XECUTE service. Time data is displayed in the users local time zone. |
| User | The user that made the change. |
| Command | The name of an associated activity area. |
| Activity Area |
The command run by the user (as actioned by the XECUTE service). |
| Resource | The Resource associated with the change (if applicable). |
| Details | Details of the change if available. |
To the left of the events grid is a panel to show XECUTE Server Statistics.
XECUTE server performs reserving and solid calculations and sends results to connected apps. The server load can spike during intensive operations, and client responsiveness may suffer while it waits for new data from the server. The Server Statistics summarises server runtime operations (processing queues) and the status of the SignalR connection.
SignalR is used to manage server to client messaging and data flows. SignalR may disconnect if there are network issues. If it remains disconnected for extended periods the XECUTE applications may show erratic behaviour where actions do not appear to save or data grids do not update.
If SignalR connection shows Disconnected or XECUTE applications show significant lags in performance you can run network and permission checks from the XECUTE menu > Test Connection.